Should not we remove https://github.com/rails/rails/tree/master/railties/test/fixtures/lib/plugin_builders and https://github.com/rails/rails/tree/master/railties/test/fixtures/lib/app_builders?

sure!

Also https://github.com/sikachu/rails/blob/c3415ada58a8cf84b6e2da6664d4aadfae885781/railties/test/generators/plugin_new_generator_test.rb#L387-393 and https://github.com/sikachu/rails/blob/c3415ada58a8cf84b6e2da6664d4aadfae885781/railties/test/generators/app_generator_test.rb#L381-387

PR updated.

whoops, hold on

Missing to remove the methods in my last comment

I ended up removed the whole class, since it's now a no-op.

❤️ 💚 💙 💛 💜

what @jokklan said +1. @sikachu why is this feature removed? Thnx!

I'll let core team speak on this one (/cc @dhh). I think we didn't see enough usage on this in the real world, so it got removed during the cleanup.

I've never used this, so I'd need some context as to what this is used for to chime in. Can anyone give some real-world examples of how and for what they're using this?

I have two cases where i used it myself: Dummy app for testing (which is generated when generating a new engine, but their does not exists any rake method to create it manually), and custom engines.

RefineryCMS is another good example where they have created a whole new custom generator for engines, instead of using all the methods already available in the internal Rails engine builder (see: engine_generator.rb and extension_generator.rb).

Another solution would be to make it simpler to make a generator with a custom builder that inherits from the existing builders, and add documentation about this.